The MDM server must implement one or more security containers on the mobile device if the mobile OS device operating system is not FIPS 140-2 validated or does not use AES for data-at-rest (DAR) encryption.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-32747	WIR-WMS-MDM-02	SV-43093r1_rule	DCNR-1	Medium

Description
The encryption module in iOS 5 is not FIPS 140-2 validated, and therefore the assurance level for data encrypted using iOS does not meet DoD requirements. A third party application must be used to provide FIPS validated encryption of sensitive DoD data to ensure it is not compromised.

STIG	Date
Mobile Device Management (MDM) Server Security Technical Implementation Guide (STIG)	2012-07-20

Details

Check Text ( C-41079r4_chk )
This is an iOS security policy set check. Recommend that all checks related to iOS security policy set rules be reviewed using the following procedure. 1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy using the following procedure: -Have the SA identify STIG compliant and non compliant policies on the server. --Log into the MDM server console. --Click on the Policies tab. --View all iOS security policies on the server. -Note: STIG-compliant policies should be identified as such in the policy title. An example is STIG_iOS_Policy. It is recommended that all non-STIG/ISCG policies be deleted. 2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. -Note: If there is a finding, note the name of the non STIG/ISCG-compliant policy in the Findings Details section in VMS/Component Provided Tracking Database. -Launch the MDM console and click on the Policies tab. -Select an iOS security policy to review. -Determine if the mobile operating system is FIPS 140-2 validated and uses AES encryption. Review vendor data sheets and the NIST web site. Note: iOS 5 and Android are currently (June 2012) not FIPS 140-2 validated. If yes, this check and checks WIR-WMS-GD-009-01 to WIR-WMS-GD-009-09 are not applicable. If no, complete the following procedures: -Verify MDM product supports FIPS 140-2 validated encryption with AES. Review vendor data sheets and the NIST web site. -Verify data-at-rest encryption is enabled in the security policy and strong user authentication is enabled in the security policy. (Review checks WIR-WMS-GD-009-01 to WIR-WMS-GD-009-09.) Mark as a finding if the mobile OS is not FIPS validated and the MDM agent does not contain a FIPS validated security container.

Check Text ( C-41079r4_chk )

This is an iOS security policy set check. Recommend that all checks related to iOS security policy set rules be reviewed using the following procedure.

1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy using the following procedure:
-Have the SA identify STIG compliant and non compliant policies on the server.
--Log into the MDM server console.
--Click on the Policies tab.
--View all iOS security policies on the server.
-Note: STIG-compliant policies should be identified as such in the policy title. An example is STIG_iOS_Policy. It is recommended that all non-STIG/ISCG policies be deleted.

2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy.
-Note: If there is a finding, note the name of the non STIG/ISCG-compliant policy in the Findings Details section in VMS/Component Provided Tracking Database.
-Launch the MDM console and click on the Policies tab.
-Select an iOS security policy to review.
-Determine if the mobile operating system is FIPS 140-2 validated and uses AES encryption. Review vendor data sheets and the NIST web site. Note: iOS 5 and Android are currently (June 2012) not FIPS 140-2 validated.
If yes, this check and checks WIR-WMS-GD-009-01 to WIR-WMS-GD-009-09 are not applicable.
If no, complete the following procedures:
-Verify MDM product supports FIPS 140-2 validated encryption with AES. Review vendor data sheets and the NIST web site.
-Verify data-at-rest encryption is enabled in the security policy and strong user authentication is enabled in the security policy. (Review checks WIR-WMS-GD-009-01 to WIR-WMS-GD-009-09.)

Mark as a finding if the mobile OS is not FIPS validated and the MDM agent does not contain a FIPS validated security container.

Fix Text (F-36625r2_fix)
Use an MDM product that supports FIPS 140-2 validated encryption and enable DAR encryption and strong user authentication in each security policy. Set each iOS security policy on the MDM server to enable the MDM profile.